chore(adopters): https://canida.io #1484
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I'd like to contribute to cdk8s. The first step that was proposed was to extend the list of adopters.
I think cdk8s is awesome because I see the following shortcomings with other approaches:
kustomize: Get's really complicated really fast. Requires a lot of search & replace when modifying manifests.
Helm: Easy to package & deploy independent services. However, it's hard to manage the interdependencies of multiple services.
In general: Hard to abstract away commonly used resources. E.g. in cdk8s I got a folder
custom-resources
which allows me to easily deploy preconfigured resources such as a new Ingress based on my custom load balancer controller. No need to copy around the configuration X times or look into 3 layers of kustomize abstractions. Just a simple class that can be modified with a handful of parameters e.g. if the ingress should be internal / public.